According to statistics, requirements management is identified as a major source of error to failed IT-projects. Moreover communication is identified as a factor affecting the require-ments management and can lead to deficiencies in the requirements. The requirements analyst is responsible for managing the requirements from the different stakeholders, act as a com-munication accommodator and to translate abstract requirements expressed by users to more specific requirements that developers can implement. The purpose of this thesis is to study the role of the requirements analyst to investigate the problems that may arise in working with requirements management.  To achieve the purpose we have performed a requirements management process in which we ourselves took the role as the requirements analysts. The requirements management process consisted of three phases: gather requirements, document requirements and validate require-ments.

AbstractBackgroundParkinson?s disease is a chronically not curable progressive disease that leads to different degrees of disability. Controlled studies on how patient education influences subjective health in Parkinson?s disease are lacking.AimThe aim of this study was to examine the influence patient education had on drug requirements and on subjective health status of persons with Parkinson?s disease.MethodologyA short form of Health Survey, SF-12, was used to measure perceived health. SF-12 was administered before and one month after patient education (intervention group; n= 48), and in waiting list control (n= 48).

The result from Requirements Engineering is a Requirements Specification. Characteristics of a good Requirements Specification are unambiguity, completeness, verifiability, consistency, modifiability, traceability, correctness and ranked for importance and/or stability.This work defines these quality attributes and answers the questions how to reach these attributes and the diffuculties which exist in this area.This work should be read to get an overwiew of the area Requirements Engineering and Requirements Specification..

Good conditions in the workplace, fairness in the workplace and the social differences contribute to a general improvement in public health. A health-promoting leader is working to create a workplace that promotes health, supports its employees and contributes to their wellbeing. The purpose of this study was to investigate the first-line managers in the city of Västerås experience and deal with their conditions and obstacles in the health-promoting leadership. A qualitative approach was chosen and the selection was six first-line managers working in three different areas of the City of Västerås. Managers were interviewed by an interviewguide and the material was analyzed with a manifest content analysis, with an inductive approach.

People spend much of their timeat work and health is affected by how we experience our everyday work situation. Health in the workplace is important for public health and seems to improve the occupational health of theemployees. The pace of work and requirements have hasincreased at work and it's not equal accepted to have an obstacle that makesyour work capacity decreases. Despite this, there are health factors that enable us meet therequirements and can maintaingood health in the workplace. Theaim of the studywas to see if there has beena change in healthcare workers work-related health over time.

As an effect of increased living standards and improved health care, life expectancy has risen in many parts of the world. At the same time, welfare diseases such as diabetes and obesity increases. As the number of elderly and long-term sick rises, so will the medical care needs. E-health applications are often presented as a way to meet future medical and doing so within the scope of existing resources. By facilitating health communication and widen access to health services by offering them online, e-health applications encourages people to become more engaged in their own health, thus working proactively towards a healthier population.

Prioritisation of software requirements is a critical part of the development of software. Whichrequirements and in which order they will be developed is one of the main tasks that requirementprioritisation supports.There are different ways that a requirement prioritisation can be used, for example alone or in agroup and with different methods.The purpose of this report is to map out how you can carry out a requirement prioritisation alonewith different types of prioritisation methods and how you solve the problems that can arise whenprioritisting requirements. This is done by documenting the use of three different types of methodsthat can be execute alone. The methods are "100-dollar test", "Ranking" and "Top-tenrequirements".To be able to prioritise requirements, you need to establish which requirements you shall prioritise.The paper retrieves this information by interviewing stakeholders in the system and analysing theresult of the interviews and the execution of the requirement prioritisation.Three problems arose during that work and I present solutions on these problems. The problemswere 1) equivalent requirements when using the "100-dollar test", 2) low differentiation gradebetween the prioritised requirements in the "100-dollar test" and 3) that the requirements that wereprioritised weren't classified before the prioritisation, which leads to inaccuracies in the resultingprioritisation.The solution to the problems that the paper presents is to increase the amount of distributable unitsin the "100-dollar test" to 1000 per requirement, suggestions of classes of the requirements andthe combination of the methods "100-dollar test" and "ranking" to bypass the equivalentrequirements.The report is written in Swedish.Nyckelord: GoTRIS, requirements retrieval, requirements analysis, Viktoria Swedish ICT,requirements prioritisation, requirements, 100-dollar test, ranking, top 10 requirements..

Requirements engineering is a widespread topic in the research field of informatics. However, there is little research regarding lack of requirements documentation and how it is perceived. The same applies for how requirements engineering in retrospect can be implemented. This is a debated issue on blogs and forums but it has not been reflected in the research area.Therefore, this study concerns research questions regarding how the developers, testers and requirements analyst experience the lack of requirements documentation and how requirements engineering in retrospect can be implemented.To answer these questions, data collection has been conducted through qualitative interviews with individuals affected by this problem in their everyday work.This study has provided an explanation of how the problem is perceived and what the consequences are, both direct and indirect. The impacts are divided into three categories and are presented as, emotional consequences, system implications and consequences regarding re source consumption.

Purpose- The purpose of this project is to contribute to the knowledge of creating customer value through streamlining and coordination of patient flows for children and youth with frequent need of care on child and youth medical clinics.Method- One of the methods used for achieving the project's purpose is a case study on the Child and Youth Medicine Clinic at Länssjukhuset Ryhov in Jönköping. The case study has been used for collecting the empirical data that has been generated through interviews, observations and documents from the Child and Youth Health Clinic. Except the case study the authors also made studies in literature, which the collected empirical data has been anchored and related to. Together this led to the project's analysis and results.Results- When investigating the questions found in chapter one, it was determined standardized work is of great importance to create structure and implement procedures for the patient flows. A weak link in the patient flow has been identified, which is the sub-process coordination and planning.

Requirements engineering is a widespread topic in the research field of informatics. However, there is little research regarding lack of requirements documentation and how it is perceived. The same applies for how requirements engineering in retrospect can be implemented. This is a debated issue on blogs and forums but it has not been reflected in the research area.Therefore, this study concerns research questions regarding how the developers, testers and requirements analyst experience the lack of requirements documentation and how requirements engineering in retrospect can be implemented.To answer these questions, data collection has been conducted through qualitative interviews with individuals affected by this problem in their everyday work.This study has provided an explanation of how the problem is perceived and what the consequences are, both direct and indirect. The impacts are divided into three categories and are presented as, emotional consequences, system implications and consequences regarding re source consumption.

Requirements engineering is a widespread topic in the research field of informatics. However, there is little research regarding lack of requirements documentation and how it is perceived. The same applies for how requirements engineering in retrospect can be implemented. This is a debated issue on blogs and forums but it has not been reflected in the research area.Therefore, this study concerns research questions regarding how the developers, testers and requirements analyst experience the lack of requirements documentation and how requirements engineering in retrospect can be implemented.To answer these questions, data collection has been conducted through qualitative interviews with individuals affected by this problem in their everyday work.This study has provided an explanation of how the problem is perceived and what the consequences are, both direct and indirect. The impacts are divided into three categories and are presented as, emotional consequences, system implications and consequences regarding re source consumption.

Good conditions in the workplace, fairness in the workplace and the social differences contribute to a general improvement in public health. A health-promoting leader is working to create a workplace that promotes health, supports its employees and contributes to their wellbeing. The purpose of this study was to investigate the first-line managers in the city of Västerås experience and deal with their conditions and obstacles in the health-promoting leadership. A qualitative approach was chosen and the selection was six first-line managers working in three different areas of the City of Västerås. Managers were interviewed by an interviewguide and the material was analyzed with a manifest content analysis, with an inductive approach.

Requirements engineering is a widespread topic in the research field of informatics. However, there is little research regarding lack of requirements documentation and how it is perceived. The same applies for how requirements engineering in retrospect can be implemented. This is a debated issue on blogs and forums but it has not been reflected in the research area.Therefore, this study concerns research questions regarding how the developers, testers and requirements analyst experience the lack of requirements documentation and how requirements engineering in retrospect can be implemented.To answer these questions, data collection has been conducted through qualitative interviews with individuals affected by this problem in their everyday work.This study has provided an explanation of how the problem is perceived and what the consequences are, both direct and indirect. The impacts are divided into three categories and are presented as, emotional consequences, system implications and consequences regarding re source consumption.

The building and plant sectors represent a large part of Sweden?s energy use. Putting energy requirements in public procurement as a tool for reducing energy consumption in the building and plant sectors is therefor an opportunity that operators can take advantage of. The aim of this thesis was to map the energy requirements in procurement that operators in the public sector use today in building and plant projects. The analysis was made with respect to if the energy requirements corresponded to the parts with large energy use in building and plant projects and also in which way energy requirements in procurement are written in the contract.

Requirements management is an important part of the software development process. The success of a project may depend on how this is handled. Even though several research studies indicates that more attention should be paid on non-functional requirements, the primary focus in practical projects still regards identifying functional requirements. Especially the prioritization of the non-functional requirements has been proven to be of great importance for the success of a project.This report investigates basics in agile requirements management involving opinions from experts from a software development company. This is done with help of existing literature and interviews with key actors involved in prioritization at the company.